Fix docstring of sphinx.util.parsing.nested_parse_to_nodes()
#14054
+5
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"section" elements can only be children of "document" or "section" elements, not "sidebar". Cf. https://docutils.sourceforge.io/docs/ref/doctree.html#section
Closed
AA-Turner
reviewed
Nov 30, 2025
AA-Turner
reviewed
Nov 30, 2025
AA-Turner
approved these changes
Nov 30, 2025
Member
|
Very sorry for the delay in reviewing this!! A |
AA-Turner
changed the title
sphinx.util.parsing.nested_parse_to_nodes()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The utility function
sphinx.util.parsing.nested_parse_to_nodes()allowsnested parsing with support for sections.
This is a "power user" feature with known problems and usage restrictions.
Purpose
Inform the user about the risks and limitations when using
nested_parse_to_nodes().References
Notes
This is a re-creation of PR #13981
without the workaround for Git re-encoding problems